@brianhelba @danlamanna I'd like to get your thoughts on 356b1da. I'm really not sure where to put this configuration logic -- because there's no one-size-fits-all tuning number for the pool size, it can't just be isolated within django-composed-configuration. We could put it there, but have it controlled by an env var, but that would involve also supporting this in our terraform module. Putting it directly in the cookiecutter makes it clear that it could / should be changed on a per-project basis, but the hard-coding feels a little odd.